← Return to doc.sitecore.com

  Config file changes in Sitecore CMS and DMS 7.1 rev. 140130 compared to CMS and DMS 7.1 rev. 130926.
Print this page (opens in new window) Print

This update requires you to make changes to the following files:

Depending on search provider you should also update appropriate files below:

The clean configuration files for Sitecore CMS and DMS 7.1 rev. 140130 can be downloaded using the following links:

Changes to the Web.config

The following changes have been made to the web.config file of Sitecore CMS 7.1 rev. 140130 (Update-1) as compared to the web.config file of Sitecore CMS 7.1 rev. 130926 (Initial Release):

  1. In the <system.webServer><handlers> section, add the following nodes, before the "sitecore_speak.ashx" node:
    <add verb="*" name="Sitecore.SpeakJS64" path="*/speak/v1/*/*.js" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv4.0,bitness64" />
          <add verb="*" name="Sitecore.SpeakJS32" path="*/speak/v1/*/*.js" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv4.0,bitness32" />
          <add verb="*" name="Sitecore.SpeakClassic64" path="sitecore_speak.ashx" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv4.0,bitness64" />
          <add verb="*" name="Sitecore.SpeakClassic32" path="sitecore_speak.ashx" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv4.0,bitness32" />

Note: The following steps are related to issues merged from 7.0 Update-4, so you do not need to make these changes if your solution was upgraded to CMS 7.1 from 7.0 Update-4 or later (but you should still update the other 7.1 configuration files as described later in this document):

  1. In the <switchingProviders><roleManager> section, add the following two attributes ignoredUserDomains="" and allowedUserDomains="" to the provider with providerName="sql". This step is optional; you can skip it unless you plan to use these attributes.
    <provider providerName="sql" storeFullNames="true" wildcard="%" domains="*" ignoredUserDomains="" allowedUserDomains="" />
  2. In the <switchingProviders><profile> section, add the following attribute ignoredDomains="" to the provider with providerName="sql". This step is optional; you can skip it unless you plan to use this attribute.
    <provider providerName="sql" storeFullNames="true" wildcard="%" domains="*" ignoredDomains="" />
  3. In the <settings> section, add the following setting, before the "Indexing.UpdateInterval " setting:
    <!--  INDEXING DISABLE DATABASE CACHES
          Indicates whether or not to populate database caches with data retrieved during indexing.
          If true, Sitecore indexes every version and language of the items as usual, but does not cache this item data in the database
          caches. This can reduce the amount of memory used for cached data and improve performance, especially in solutions with a large
          number of items, versions, and languages.
          If false, Sitecore indexes every version and language of the items and caches the item data in the database caches.
          Default value: false
    -->
    <setting name="Indexing.DisableDatabaseCaches" value="false" />
  4. In the <settings> section, add the following setting, before the "Languages.AutoRemoveItemData" setting:
    <!--  LANGUAGES ALWAYS STRIP LANGUAGE
          This setting specifies if the StripLanguage processor in the <preprocessRequest> pipeline will parse and remove languages from
          the URL, even when the languageEmbedding attribute of the linkProvider is set to "never". You should only change this setting
          to "false" if the default behavior causes problems in your solution.
          Default value: true
    -->
    <setting name="Languages.AlwaysStripLanguage" value="true" />
  5. In the <settings> section, add the following setting, before the "Login.DisableChangePassword" setting:
    <!--  LOGIN DISABLE AUTOCOMPLETE
          If true, an autocomplete="off" attribute is added on the Sitecore login forms on the /sitecore/login/default.html and
          /sitecore/admin/login.html pages. This is useful, for example, if you don’t want user names to be disclosed when editors
          log into Sitecore on shared/public computers.
          Default value: false
    -->
    <setting name="Login.DisableAutoComplete" value="false" />
  6. In the <settings> section, add the following setting, after the "Login.DisablePasswordRecovery" setting:
    <!--  LOGIN DISABLE REMEMBER ME
          If true, Sitecore disables the "Remember me" checkbox on the login page.
          Default: false
    -->
    <setting name="Login.DisableRememberMe" value="false" />
  7. Note: The following steps should only be performed if you have configured your solution to use the Sitecore serialization event handlers which automatically serialize item changes. If you are using these event handlers, you must add two event handlers to the configuration. Add the following event handler to the <event name="item:copied"> node:
    <event name="item:copied">
      <handler type="Sitecore.Data.Serialization.ItemHandler, Sitecore.Kernel" method="OnItemCopied"/>
    </event>
    And add the following event handler to the <event name="item:renamed"> node:
    <event name="item:renamed">
      <handler type="Sitecore.Data.Serialization.ItemHandler, Sitecore.Kernel" method="OnItemRenamed"/>
    </event>

Note: The following steps are related to issues merged from 7.0 Update-3, so you do not need to make these changes if your solution was upgraded to CMS 7.1 from 7.0 Update-3 or later (but you should still update the other 7.1 configuration files as described later in this document):

  1. In the <publish> pipeline, add a new processor of type RaiseQueuedEvents between processors of type AddItemsToQueue and ProcessQueue:
    <publish help="Processors should derive from Sitecore.Publishing.Pipelines.Publish.PublishProcessor">
      <processor type="Sitecore.Publishing.Pipelines.Publish.AddLanguagesToQueue, Sitecore.Kernel"/>
      <processor type="Sitecore.Publishing.Pipelines.Publish.AddItemsToQueue, Sitecore.Kernel"/>
      <processor type="Sitecore.Publishing.Pipelines.Publish.RaiseQueuedEvents, Sitecore.Kernel"/>
      <processor type="Sitecore.Publishing.Pipelines.Publish.ProcessQueue, Sitecore.Kernel"/>
    </publish>

Changes to the App_Config\Commands.config

The following changes have been made to the App_Config\Commands.config file of Sitecore CMS 7.1 rev. 140130 (Update-1) as compared to the App_Config\Commands.config file of Sitecore CMS 7.1 rev. 130926 (Initial Release).

  1. Note: The following steps are related to issues merged from 7.0 Update-3, so you do not need to make these changes if your solution was upgraded to CMS 7.1 from 7.0 Update-3 or later (but you should still update the other 7.1 configuration files as described later in this document):
    Add the following command after the "contenteditor:incrementmark" command: 
    <command name="contenteditor:navigate" type="Sitecore.Shell.Framework.Commands.ContentEditor.Navigate,Sitecore.Kernel" />

Changes to the App_Config\Include\Sitecore.AntiCsrf.config
The following changes have been made to the App_Config\Include\Sitecore.AntiCsrf.config file of Sitecore CMS 7.1 rev. 140130 (Update-1) as compared to the App_Config\Include\Sitecore.AntiCsrf.config file of Sitecore CMS 7.1 rev. 130926 (Initial Release):

  1. In the <rule name="shell"> section, remove the following node:
    <ignore contains="TreeviewEx"/>

Changes to the App_Config\Include\Sitecore.ContentSearch.config

The following changes have been made to the App_Config\Include\Sitecore.ContentSearch.config file of Sitecore CMS 7.1 rev. 140130 (Update-1) as compared to the App_Config\Include\Sitecore.ContentSearch.config file of Sitecore CMS 7.1 rev. 130926 (Initial Release).

Note: The following steps are related to issues merged from 7.0 Update-4, so you do not need to make these changes if your solution was upgraded to CMS 7.1 from 7.0 Update-4 or later (but you should still update the other 7.1 configuration files as described later in this document):

  1. In the <settings> section, add the following setting (you can add it at any place in the section, but in a clean Sitecore installation the new node is placed before the “ContentSearch.ParallelIndexing.Enabled" setting):
    <!--  INDEXING DISABLE DATABASE CACHES
          Indicates whether or not to populate database caches with data retrieved during indexing.
          If true, Sitecore indexes every version and language of the items as usual, but does not cache this item data in the database
          caches. This can reduce the amount of memory used for cached data and improve performance, especially in solutions with a large
          number of items, versions, and languages.
          If false, Sitecore indexes every version and language of the items and caches the item data in the database caches.
          Default value: false
    -->
    <setting name="ContentSearch.Indexing.DisableDatabaseCaches" value="false"/>
  2. In the <settings> section, replace the following node:
    <!--  PARALLEL INDEXING CORE LIMIT
          Restrict parallel indexing to a certain number of cores.
          ('0' = no limit.)
    -->
    <setting name="ContentSearch.ParallelIndexing.LimitCores" value="3" />
    with:
    <!--  PARALLEL INDEXING MAX THREAD LIMIT
          This setting allows you to limit the number of threads used for indexing operations when parallel indexing is enabled.
          If the value is set to 0, there is no limit to the number of threads.
          Default value: 3
    -->
    <setting name="ContentSearch.ParallelIndexing.MaxThreadLimit" value="3" />

Changes to the App_Config\Include\Sitecore.Buckets.config

The following changes have been made to the App_Config\Include\Sitecore.Buckets.config file of Sitecore CMS 7.1 rev. 140130 (Update-1) as compared to the App_Config\Include\Sitecore.Buckets.config file of Sitecore CMS 7.1 rev. 130926 (Initial Release).

Note: The following steps are related to issues merged from 7.0 Update-4, so you do not need to make these changes if your solution was upgraded to CMS 7.1 from 7.0 Update-4 or later (but you should still update the other 7.1 configuration files as described later in this document):

  1. In the <databases> section, add a new node for the core database (you can add it at any place in the section, but in a clean Sitecore installation the new node is placed before the node with the master database):
    <database id="core" singleInstance="true" type="Sitecore.Data.Database, Sitecore.Kernel">
      <Engines.DataEngine.Commands.AddFromTemplatePrototype>
        <obj type="Sitecore.Buckets.Commands.AddFromTemplateCommand, Sitecore.Buckets" />
      </Engines.DataEngine.Commands.AddFromTemplatePrototype> 
    </database>

Note: The following steps are related to issues merged from 7.0 Update-3, so you do not need to make these changes if your solution was upgraded to CMS 7.1 from 7.0 Update-3 or later (but you should still update the other 7.1 configuration files as described later in this document):

  1. In the <buckets.cloneItemIntoBucket> pipeline, add a new processor of type ProcessParentReference after the existing processor:
    <!-- CLONE ITEM INTO BUCKET PIPELINE
         Pipeline for cloning items into an item bucket.
         Arguments : (Item) Source, (Item) Target, (bool) Whether or not cloning was successful, (bool) Deep check.
    -->
    <buckets.cloneItemIntoBucket>
      <processor type="Sitecore.Buckets.Pipelines.ItemOperations.CloneItem.RunCloning, Sitecore.Buckets"/>
      <processor type="Sitecore.Buckets.Pipelines.ItemOperations.CloneItem.ProcessParentReference, Sitecore.Buckets"/>
    </buckets.cloneItemIntoBucket>
  2. In the <buckets.copyItemIntoBucket> pipeline, add a new processor of type ProcessParentReference after the existing processor:
    <!-- COPY ITEM INTO BUCKET PIPELINE
         Pipeline for copying items into an item bucket.
         Arguments : (Item) The item to add a search tab to. (bool) Whether the tab was added or not.
    -->
    <buckets.copyItemIntoBucket>
      <processor type="Sitecore.Buckets.Pipelines.ItemOperations.CopyItem.RunCopying, Sitecore.Buckets"/>
      <processor type="Sitecore.Buckets.Pipelines.ItemOperations.CopyItem.ProcessParentReference, Sitecore.Buckets"/>
    </buckets.copyItemIntoBucket>
  3. In the <buckets.moveItemIntoBucket> pipeline, add a new processor of type ProcessParentReference after the existing processor:
    <!-- MOVE ITEM INTO BUCKET PIPELINE
               Pipeline for moving items into or out of an item bucket. This pipeline also makes sure that the item being moved is “bucketable”. If it is bucketable, it is automatically bucketed after it has been moved.
               Arguments : (Item) The item being moved. (bool) Whether the item was moved successfully or not.
          -->
          <buckets.moveItemIntoBucket>
            <processor type="Sitecore.Buckets.Pipelines.ItemOperations.MoveItem.RunMoving, Sitecore.Buckets"/>
            <processor type="Sitecore.Buckets.Pipelines.ItemOperations.MoveItem.ProcessParentReference, Sitecore.Buckets"/>
          </buckets.moveItemIntoBucket>
  4. In the <pipelines> section, add the following pipeline:
    <!-- EXPAND ID-BASED SEARCH FILTERS
         Sitecore executes this pipeline for search filters when their Client Side Hook is set to "id". To display a user-friendly item name
         in the UI, the ExpandIds processor replaces "<ID>" with "<Item Display Name>|<ID>" in these search filters.
    -->
    <buckets.expandIdBasedSearchFilters>
      <processor type="Sitecore.Buckets.Pipelines.UI.ExpandIdBasedSearchFilters.ExpandIds, Sitecore.Buckets"/>
    </buckets.expandIdBasedSearchFilters>
  5. In the <settings> section, remove the "BucketConfiguration.EnableSearchTips" setting:
    <!-- ENABLE SEARCH TIPS IN UI
         This setting globally disables tips for every user. If you want to disable tips at the user level, use the User Manager.
    -->
    <setting name="BucketConfiguration.EnableSearchTips" value="true"/>

Changes to the App_Config\Include\Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config

The following changes have been made to the App_Config\Include\Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file of Sitecore CMS 7.1 rev. 140130 (Update-1) as compared to the App_Config\Include\Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file of Sitecore CMS 7.1 rev. 130926 (Initial Release).

Note: The following steps are related to issues merged from 7.0 Update-3, so you do not need to make these changes if your solution was upgraded to CMS 7.1 from 7.0 Update-3 or later (but you should still update the other 7.1 configuration files as described later in this document):

  1. In the <fieldMap><fieldNames> section, add a new field mapping for the "site" computed field (you can add it at any place in the section, but in a clean Sitecore installation the new node is placed between the "_group" and "_latestversion" nodes):
    <field fieldName="site" 
    storageType="YES" indexType="TOKENIZED"    vectorType="NO" boost="1f" type="System.String" settingType="Sitecore.ContentSearch.LuceneProvider.LuceneSearchFieldConfiguration, Sitecore.ContentSearch.LuceneProvider">
      <analyzer type="Sitecore.ContentSearch.LuceneProvider.Analyzers.LowerCaseKeywordAnalyzer, Sitecore.ContentSearch.LuceneProvider" />
    </field>
  2. In the <defaultIndexConfiguration> section, add a new <mediaIndexing> node:
    <!-- MEDIA ITEM CONTENT EXTRACTOR FILE MAPPING
         This map allows you to specify the extensions and mimetypes that we will pass through to the IFilters on your machine so they can be indexed.
         We also allow you to include all files or exclude all files and leave it to the IFilters to control what is and is not indexed.
    -->
    <mediaIndexing hint="raw:AddMediaIndexingMap">
      <mimeTypes>
        <excludes>
          <mimeType>*</mimeType>
        </excludes>
        <includes>
          <mimeType>application/pdf</mimeType>
          <mimeType type="Sitecore.ContentSearch.ComputedFields.MediaItemHtmlTextExtractor, Sitecore.ContentSearch">text/html</mimeType>
          <mimeType>text/plain</mimeType>
        </includes>
      </mimeTypes>
      <extensions>
        <excludes>
          <extension>*</extension>
        </excludes>
        <includes>
          <extension>rtf</extension>
          <extension>odt</extension>
          <extension>doc</extension>
          <extension>dot</extension>
          <extension>docx</extension>
          <extension>dotx</extension>
          <extension>docm</extension>
          <extension>dotm</extension>
          <extension>xls</extension>
          <extension>xlt</extension>
          <extension>xla</extension>
          <extension>xlsx</extension>
          <extension>xlsm</extension>
          <extension>xltm</extension>
          <extension>xlam</extension>
          <extension>xlsb</extension>
          <extension>ppt</extension>
          <extension>pot</extension>
          <extension>pps</extension>
          <extension>ppa</extension>
          <extension>pptx</extension>
          <extension>potx</extension>
          <extension>ppsx</extension>
          <extension>ppam</extension>
          <extension>pptm</extension>
          <extension>potm</extension>
          <extension>ppsm</extension>
        </includes>
      </extensions>
    </mediaIndexing>
  3. In the <defaultIndexConfiguration> section, add a new <documentBuilderType> node:
    <!-- DOCUMENT BUILDER
         Allows you to override the document builder. The document builder class processes all the fields in the Sitecore items and prepares
         the data for storage in the index.
         You can override the document builder to modify how the data is prepared, and to apply any additional logic that you may require.
    -->
    <documentBuilderType>Sitecore.ContentSearch.LuceneProvider.LuceneDocumentBuilder, Sitecore.ContentSearch.LuceneProvider</documentBuilderType>
  4. Optional: Replace the description of the computed index fields:
    <!-- COMPUTED INDEX FIELDS
         This setting allows you to add fields to the index that contain computed values that are based on the item that is being indexed.
    -->
    with
    <!-- COMPUTED INDEX FIELDS
         This setting allows you to add fields to the index that contain values that are computed for the item that is being indexed.
         You can specify the storageType and indextype for each computed index field in the <fieldMap><fieldNames> section.
    -->
  5. Optional: Remove all "storageType" and "indexType" attributes from the <field hint="raw:AddComputedIndexField"> section, since these attributes are not used by the system. In a clean Sitecore installation, the section now looks like this:
    <fields hint="raw:AddComputedIndexField">
      <field fieldName="_content"                       >Sitecore.ContentSearch.ComputedFields.MediaItemContentExtractor,Sitecore.ContentSearch</field>
      <field fieldName="calculateddimension"            >Sitecore.ContentSearch.ComputedFields.CalculatedDimension,Sitecore.ContentSearch</field>
      <field fieldName="daterange_month"                >Sitecore.ContentSearch.ComputedFields.DateRangeMonthFacet,Sitecore.ContentSearch</field>
      <field fieldName="daterange_week"                 >Sitecore.ContentSearch.ComputedFields.DateRangeWeekFacet,Sitecore.ContentSearch</field>
      <field fieldName="daterange_year"                 >Sitecore.ContentSearch.ComputedFields.DateRangeYearFacet,Sitecore.ContentSearch</field>
      <field fieldName="istemplate"                     >Sitecore.ContentSearch.ComputedFields.IsTemplate,Sitecore.ContentSearch</field>
      <field fieldName="lock"                           >Sitecore.ContentSearch.ComputedFields.IsLocked,Sitecore.ContentSearch</field>
      <field fieldName="parsedcreatedby"                >Sitecore.ContentSearch.ComputedFields.ParsedCreatedBy,Sitecore.ContentSearch</field>
      <field fieldName="parsedupdatedby"                >Sitecore.ContentSearch.ComputedFields.ParsedUpdatedBy,Sitecore.ContentSearch</field>
      <field fieldName="parsedlanguage"                 >Sitecore.ContentSearch.ComputedFields.ParsedLanguage,Sitecore.ContentSearch</field>
      <field fieldName="site"                           >Sitecore.ContentSearch.ComputedFields.Site,Sitecore.ContentSearch</field>
      <field fieldName="sizerange"                      >Sitecore.ContentSearch.ComputedFields.FileSizeGrouping,Sitecore.ContentSearch</field>
      <field fieldName="version"                        >Sitecore.ContentSearch.ComputedFields.StoreVersionTermVector,Sitecore.ContentSearch</field>
      <field fieldName="urllink"                        >Sitecore.ContentSearch.ComputedFields.UrlLink,Sitecore.ContentSearch</field>
      <field fieldName="isbucket_text"                  >Sitecore.ContentSearch.ComputedFields.IsBucket,Sitecore.ContentSearch</field>
      <!-- Disabled for speed of indexing. Enable if you would like to query by the fields below -->
      <!--<field fieldName="_isclone"                   >Sitecore.ContentSearch.ComputedFields.IsClone,Sitecore.ContentSearch</field>-->
      <!--<field fieldName="_links"                     >Sitecore.ContentSearch.ComputedFields.ItemLinks, Sitecore.ContentSearch</field>-->
      <!--<field fieldName="_templates"                 >Sitecore.ContentSearch.ComputedFields.AllTemplates, Sitecore.ContentSearch</field>-->
      <!--<field fieldName="hasactivetest"              >Sitecore.ContentSearch.ComputedFields.IsBeingTested,Sitecore.ContentSearch</field>-->
      <!--<field fieldName="hasclones"                  >Sitecore.ContentSearch.ComputedFields.HasClones,Sitecore.ContentSearch</field>-->
      <!--<field fieldName="haspublishingrestrictions"  >Sitecore.ContentSearch.ComputedFields.HasPublishingRestrictions,Sitecore.ContentSearch</field>-->
      <!--<field fieldName="isinworkflow"               >Sitecore.ContentSearch.ComputedFields.IsItemInWorkflow,Sitecore.ContentSearch</field>-->
      <!--<field fieldName="persona"                    >Sitecore.ContentSearch.ComputedFields.PersonaMatch,Sitecore.ContentSearch</field>-->
    </fields>

Changes to the App_Config\Include\Sitecore.ContentSearch.Solr.Indexes.config
The following changes have been made to the App_Config\Include\Sitecore.ContentSearch.Solr.Indexes.config file of Sitecore CMS 7.1 rev. 140130 (Update-1) as compared to the App_Config\Include\Sitecore.ContentSearch.Solr.Indexes.config file of Sitecore CMS 7.1 rev. 130926 (Initial Release).

Note: The following steps are related to issues merged from 7.0 Update-3, so you do not need to make these changes if your solution was upgraded to CMS 7.1 from 7.0 Update-3 or later:

  1. In the <defaultIndexConfiguration> section, add a new <mediaIndexing> node:
    <!-- MEDIA ITEM CONTENT EXTRACTOR FILE MAPPING
         This map allows you to specify the extensions and mimetypes that we will pass through to the IFilters on your machine so they can be indexed.
         We also allow you to include all files or exclude all files and leave it to the IFilters to control what is and is not indexed.
    -->
    <mediaIndexing hint="raw:AddMediaIndexingMap">
      <mimeTypes>
        <excludes>
          <mimeType>*</mimeType>
        </excludes>
        <includes>
          <mimeType>application/pdf</mimeType>
          <mimeType type="Sitecore.ContentSearch.ComputedFields.MediaItemHtmlTextExtractor, Sitecore.ContentSearch">text/html</mimeType>
          <mimeType>text/plain</mimeType>
        </includes>
      </mimeTypes>
      <extensions>
        <excludes>
          <extension>*</extension>
        </excludes>
        <includes>
          <extension>rtf</extension>
          <extension>odt</extension>
          <extension>doc</extension>
          <extension>dot</extension>
          <extension>docx</extension>
          <extension>dotx</extension>
          <extension>docm</extension>
          <extension>dotm</extension>
          <extension>xls</extension>
          <extension>xlt</extension>
          <extension>xla</extension>
          <extension>xlsx</extension>
          <extension>xlsm</extension>
          <extension>xltm</extension>
          <extension>xlam</extension>
          <extension>xlsb</extension>
          <extension>ppt</extension>
          <extension>pot</extension>
          <extension>pps</extension>
          <extension>ppa</extension>
          <extension>pptx</extension>
          <extension>potx</extension>
          <extension>ppsx</extension>
          <extension>ppam</extension>
          <extension>pptm</extension>
          <extension>potm</extension>
          <extension>ppsm</extension>
        </includes>
      </extensions>
    </mediaIndexing>
  2. In the <defaultIndexConfiguration> section, add a new <documentBuilderType> node:
    <!-- DOCUMENT BUILDER
         Allows you to override the document builder. The document builder class processes all the fields in the Sitecore items and prepares
         the data for storage in the index.
         You can override the document builder to modify how the data is prepared, and to apply any additional logic that you may require.
    -->
    <documentBuilderType>Sitecore.ContentSearch.SolrProvider.SolrDocumentBuilder, Sitecore.ContentSearch.SolrProvider</documentBuilderType> 
  3. Optional: Replace the description of the computed index fields:
    <!-- COMPUTED INDEX FIELDS
         This setting allows you to add fields to the index that contain computed values that are based on the item that is being indexed.
    -->
    with
    <!-- COMPUTED INDEX FIELDS
         This setting allows you to add fields to the index that contain values that are computed for the item that is being indexed.
         You can specify the storageType and indextype for each computed index field in the <fieldMap><fieldNames> section.
    -->

Changes to the shell\Applications\Reports\Dashboard\Configuration.config

The following changes have been made to the shell\Applications\Reports\Dashboard\Configuration.config file of Sitecore CMS 7.1 rev. 140130 (Update-1) as compared to the shell\Applications\Reports\Dashboard\Configuration.config file of Sitecore CMS 7.1 rev. 130926 (Initial Release).

  1. Before the <QueryItems> section, add a new <ignoreSites> node:
    <ignoreSites>
      <site name = "shell" />
      <site name = "login" />
      <site name = "admin" />
      <site name = "service" />
      <site name = "modules_shell" />
      <site name = "modules_website" />
      <site name = "scheduler" />
      <site name = "system" />
      <site name = "publisher" />
      <site name = "speak" />
    </ignoreSites>